home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Monster Media 1996 #15
/
Monster Media Number 15 (Monster Media)(July 1996).ISO
/
maximus
/
nmfw205.zip
/
NMFWD.CFG
< prev
next >
Wrap
Text File
|
1996-06-18
|
28KB
|
706 lines
;*****************************************************************************
;* *
;* (C) Copyright 1991-1996 Alberto Pasquale *
;* *
;* A L L R I G H T S R E S E R V E D *
;* *
;*****************************************************************************
;* *
;* NmFwd is NOT free-software, it is distributed under the ShareWare *
;* concept ! If you regularly use it, you should register. *
;* See REGISTER.DOC for more details on how to register your copy. *
;* *
;*****************************************************************************
;* *
;* How to contact the author: Alberto Pasquale of 2:332/504@fidonet *
;* alberto.pasquale@mo.nettuno.it *
;* Viale Verdi 106 *
;* 41100 Modena *
;* Italy *
;* *
;*****************************************************************************
;
;
; Sample NmFwd 2.05 Control file
;
;
;RegKey RegistrationKey ; If you are a registered user, put your
; ; registration key here (not case sensitive)
;
;
; S Y S T E M
;
;
; MaxPrm <filename>
;
; Points to the Maximus 3.xx PRM file.
; If the MAXIMUS environment variable is defined, this statement is an
; optional override.
;
MaxPrm c:\max\max.prm ; Maximus Prm file
;
; MultiLineDesc <nnn> [<c>]
;
; Specifies the continuation column (0 based) and character
; for multi-line descriptions in files.bbs.
;
; For example, to have the 2nd and following description lines in
; files.bbs preceded by 31 spaces, use:
;
; MultiLineDesc 31
;
; To have the continuation lines preceded by a
; '|' character, use:
;
; MultiLineDesc 29 |
;
MultiLineDesc 31
;
; The "SquishCfg" file is changed by Areafix.
; Some cfg options are searched for in SquishCfg:
; Address, BinkPoint, NetFile, NetArea, PointNet, LogFile, Outbound,
; Password, Maxpkt, KillInTransit, Track
;
; If you want to add or override some option, you can add any of the
; previous statements in this file. The overrides must be after the
; SquishCfg statement, so that they can overwrite the specifications
; previously got from the Squish cfg file.
;
; ATTENTION: the log file is opened when a logfile specification is first
; encountered. If you want to override the LogFile statement of squish.cfg
; you must specify "LogFile" before "SquishCfg" !
; The "-l<logfile>" command line swith is a global override.
;
; The new "include" statement of squish.cfg is NOT supported: you must
; use a unique Squish.Cfg file if you want NmFwd to work correctly.
;
SquishCfg c:\max\squish.cfg ; The Squish configuration file.
;
;
; If you have the "BinkPoint" verb active in SquishCfg, NmFwd must know
; which points (if any) have to be addressed using the 3D fakenet
; address.
; The "3DPoint <point> [<point>] ..." statement allows you to give NmFwd
; the necessary information.
; Multiple 3DPoint lines are allowed.
; If "BinkPoint" is not used (Squish in 3D mode) NmFwd assumed that all
; the points are 3D, so that you can comment out the 3DPoint statement.
;
3DPoint 1 2 4 5 6 ; List of fakenet Points
;
;
TmpPath c:\nmtmp ; Path for temporary files
;
;
MsgSize 16000 ; set the maximum size for messages generated
; ; by the various robots: defaults to 7000.
; ; Output will be automatically divided into
; ; multiple messages of this size.
;
FwdMsgSize 260000 ; set the size of the message forward buffer.
; ; Defaults to 32000
; ; Forwarded netmail messages will be truncated
; ; at this size, so make sure this number is large
; ; enough (as the buffer of your mail processor).
;
MarkReceived ; Mark the messages addressed to the various
; ; robots as received. Otherwise they are deleted
; ; after execution.
; ; !!! If you have problems with NmFwd and Golded,
; ; please be sure this statement is active.
;
; WrapDesc [<indent> [<right>]] ; Allows to indent the file descriptions
; reported by the filemanager.
; <indent> is the indentation for 2nd
; and consecutive lines (default 0);
; <right> is the maximum column number
; (default 79).
;
WrapDesc 31 79 ; Align file description
;
;
;
; B O S S E N A B L E
;
;
; If you are a remote SysOp and you usually operate from your point, you
; should be aware that you cannot send netmail messages with the ".0"
; address from your 4D point through your Boss, as you could with a 3D
; point. The reason is that Squish (on your Boss) automatically adds
; any missing "^AFMPT n" kludge to all messages tossed from PKTs that
; come from 4D points.
;
; So, if you need the capability to send netmail messages to Areafix,
; Raid, VoteMgr of your uplinks from your point, you need the BossEnable
; verb.
;
; When BossEnable is active, if a netmail message coming from one of
; your points has the "*BOSS*" (case insensitive) string at the beginning
; of its subject, the string and the "^AFMPT n" kludge are removed.
;
; No space is removed after the "*BOSS*" string, so don't leave any
; space between this string and the actual subject if you do not need
; spaces before the subject !
;
;
BossEnable ; Enables .0 netmail msgs from 4D points
;
;
;
; B O S S R O U T I N G
;
;
; If you are using BinkleyTerm (TradeMark of Bit Bucket Software)
; in the 5D mode (no "privatenet" in binkley.cfg) and Squish in 4D mode
; ("BinkPoint" in squish.cfg) you should have noted that you cannot
; send a crash netmail to a point through its boss, as you could in a
; fakenet environment.
;
; If you do not comment out the "BossRoute" statement, NmFwd will send
; to your Outbound.Sq and route to their boss all the crash and direct
; flavoured messages addressed to points that are not found in your V7
; nodelist or that have a NULL phone number.
;
; Thus you have the good old boss-routing feature while retaining the
; capability of directly calling a point if it has a valid phone number
; in your V7 nodelist. Please note that a point in your nodelist could
; have been redirected to its boss: in this case Binkley will call it
; through its boss phone number.
;
BossRoute ; Route Crash/Direct msgs for points to their boss
;
;
;
; B O S S F I X
;
;
; Squish 1.01 has a bug: when operating in 4D mode, the messages
; addressed to points are automatically routed to their Boss BUT Squish
; does NOT set the packet password for the Boss in the routed packet.
;
; So, if you are operating in 4D mode using packet passwords and you
; have some downlinks, you cannot use the
; "Send <flavour> <node> [<nodes>...]" command in route.cfg.
; You can safely use the "Route <flavour> <node> .All" command for each
; of your downlinks (explicitly routing points to their Boss).
;
; An easier way is to enable the "BossFix" statement provided by NmFwd:
; all the normal flavoured messages addressed to points are routed to
; their Boss by NmFwd. The messages are packed to *.OUT in Outbound.Sq
; and they receive the correct packet password.
;
; Not necessary with Squish 1.11
;
; BossFix
;
;
;
; F L A G S T R I P P I N G
;
;
; If you comment out the CM_from statement, the Crash and Direct
; flags of original messages will not be touched.
; If you use it, the CM flag will be stripped from any message not coming
; from the specified points. If you don't specify any point, the flag
; will be stripped from all the messages.
;
; The DM_from statement is ignored if CM_from is commented out.
; If DM_from is commented out, all systems are allowed the Direct flag.
; If DM_from is used, the Direct flag is not allowed, except for the
; specified points.
;
; Note: The Direct flag is the sum of Crash and Hold flags for Squish !
;
; If you use these statements, you should disable any flag stripping
; capability of Squish (comment out the StripAttributes in Squish.cfg).
;
CM_from 0 1 2 ; SysOp/CoSysOp points can send CM and DM through
; ; the BOSS.
; ; Point 0 allows non-local msgs with Boss' address to
; ; get through the Boss with the crash or direct flag
; ; (e.g. a SysOp who sends a msg from his point with
; ; his BBS address).
DM_from 4 5 ; AsstSysOp points can send DM through the BOSS
DM_from 18 ; You can use multiple CM_from/DM_from statements.
; ; (max 40 points in CM_from/DM_from statements (40+40)).
;
;
;
; M A T R I X F O R W A R D
;
;
; If you want to send a copy of ALL matrix messages to some point, you
; must put the point numbers in the following statement
; "FwdAll <point> [<point>] ...".
;
; All matrix messages neither coming nor addressed to "<point>" will be
; forwarded to it.
;
; If you don't need to forward ALL matrix msgs to any point, you can comment
; out the "FwdAll" statement.
;
; The "FwdLoc" and "FwdBbs" statements allow a more controlled forwarding.
;
;
FwdAll 1 ; Points that must receive ALL matrix msgs
;
FwdLoc 2 ; Points that must receive the messages
; ; from/to your BBS (and points) _only_
; ; (no in-transit message will be forwarded).
;
;FwdBbs 2 ; Points that must receive the messages
; ; from/to your BBS (no points) _only_.
;
;
;
; P O I N T R E M A P P I N G
;
;
; The "from address" of every read message coming from your 3D (fakenet)
; points is internally remapped to 4D.
;
; The "Remap <point> <name>" statement allows you to remap messages
; addressed to your system (.0) to <point> if a match is found
; with <name>. You can use the Remap statement both here and in Squish.Cfg
; (if you want to use the advanced full-address remapping feature of Squish).
; However you MUST use the Remap statement provided by NmFwd for all
; the points listed in FwdAll, FwdLoc and FwdBbs statements (otherwise
; these points may receive dupes (the original remapped by Squish and
; the forwarded copy sent by NmFwd).
; Other points can be remapped here and/or in Squish.cfg, however you are
; strongly encouraged to remap all your points here.
;
Remap 1 Alberto Pasquale
Remap 1 SysOp
Remap 2 Roberto Zanasi
Remap 3 Francesco Carta
Remap 4 Massimo Morselli
Remap 5 Tiziano Incerti
;
;
;
; F I L E A T T A C H
;
;
; All File Attaches addressed to your points are handled by NmFwd,
; since all netmail messages to your points are directly forwarded by
; NmFwd. The "FileForward" statement allows the file forwarding to the
; listed points. However the F/As to .0 will not be forwarded, even if the
; message is remapped to one of your points. This is a feature not a
; limit.
;
FileForward All ; allow file forwarding to any point
;
;FileForward 1 2 3 ; allow file forwarding to the listed points
;
; Some point users like sending files to other points through the Boss.
; This can be annoying for the busy SysOp that has to keep track
; of inbound files sent by points and to delete them after they have been
; sent to the destination point(s).
;
; Now you can use the Tmp_Fa_Dir as a temporary directory for the F/As
; between your points: all files in one of your NetFile directories that
; have a F/A message between two of your points will be moved (and
; touched) to the Tmp_Fa_Dir.
; If a file with the same name exists, it is overwritten.
;
; If you use the Tmp_Fa_Kill option, the files in Tmp_Fa_Dir will be deleted
; after the specified number of days. Under HPFS (OS/2) you can choose
; how to compute the file age: you can specify "Creation" (for Creation
; date) or "Write" (for Last-Write date). If none specified, Creation
; is assumed since it's usually handled as the "upload" date.
;
; The files with messages addressed to .0 will not be moved, even if they
; are remapped to some point.
;
Tmp_Fa_Dir c:\file\tmpfa
;
Tmp_Fa_Kill 10 Creation
;
;
; My points like sending me new files thru F/A, instead of uploading them as
; users. So my CoSysOp has to move these files to the appropriate upload
; directory and add to the files.bbs the description the point has sent
; via netmail.
;
; Now you can instruct Nmfwd to move the files and add the descriptions
; for you.
;
; UpFa <upname> <updir> [<points>]
;
; Allows to move (and touch) to <updir> the files (in one of your
; NetFile dirs) whose F/A is addressed to <upname> at one of your
; addresses. The descriptions are appended to the <updir>\files.bbs
; file. Files with the same name are overwritten. The descriptions
; must be in the form of a single line of message text:
; "<filename> <description>".
;
; Pippo.Gif Another Gif Picture 2048*4096 50331648 colours
;
; In the case of a multiple F/A (with the same msg) the various descriptions
; can be put on different lines of the same message.
; <filename> can be shortened by completing it with *, so that you could write:
;
; Pip* Another Gif Picture ...
; or
; * Another Gif Picture ...
;
; The second example is very convenient in the case of a single F/A.
;
; The message is forwarded to all the points listed in "FwdAll", "FwdLoc"
; or "FwdBbs" statements and to those that are optionally listed in
; the "UpFa" line (<points>).
;
UpFa Upload c:\file\upload 2 18 ; max 20 UpFa statements
UpFa UpAmiga d:\file\upamiga
UpFa UpAtari d:\file\upatari 5
UpFa UpMac d:\file\upmac 20
UpFa Private d:\file\private 18
;
;
; ***********************************************************************
; ** From here on, if you want a copy of answer messages on the Boss, **
; ** you can specify 0 as a point number. **
; ***********************************************************************
;
; R E T U R N T O S E N D E R
;
; (Version 7 nodelist)
;
; If active, checks the from and to address of all netmail messages.
;
RTS ; To enable Return To Sender functions
;
RTSAnswer 1 0 ; RTS messages are forwarded to these points
;
NoRoutedEcho ; To stop Routed Echomail
;
Nodelist c:\max\nodex ; Base name (no extension) of Version7 nodelist files.
; ; Multiple statements allowed (NmFwd will search all
; ; defined nodelists).
;
;
; RETURN RECEIPT
;
RRQ ; enables Return Receipts
;
RRQAnswer 1 ; Return Receipts are forwarded to these points
;
;
;
; U S E R M A N A G E M E N T
;
; (Max 3.xx)
;
; You can modify the user file by a netmail message addressed to one of
; the following "robots" at one of your addresses (max 10 RemUser
; statements).
; The message must have the necessary password as its subject; the text
; contains the commands. See the .DOC for details on available commands.
;
; ATTENTION: The robot's answers are sent to the points listed at the end
; of "RemUser" statements ONLY (not to the sender). Of course the legitimate
; user of the <password> must be listed in <points>.
;
; RemUser <name> <pwd> [<points>]
;
; where:
;
; <name> is the UserManager robot name to which netmail messages must be
; addressed (19 chars max).
;
; <pwd> is the password to be used in the subject field of the netmail
; (19 chars max).
;
; <points> is the list of points that must receive the answers.
;
; E.g.:
;
; RemUser Raiser SysOpPwd 0 2
;
; Specifies that a Remote UserManager robot named "Raiser" can be
; addressed using the "SysOpPwd" password in the subject of the netmail
; and the answers must be written to the local netmail base ('0') and
; sent to point 2 ('2').
;
RemUser Raiser password 1 2
;
MaxLev Extra ; Max privilege RemUser is allowed to operate on.
; ; (Users with a priv level above MaxLev are skipped)
; ; Any privilege name defined in Maximus Access.Ctl
; ; can be specified as well as any level number.
;
;
;
; F I L E M A N A G E M E N T
;
; (Max 3.xx)
;
; You can handle your file areas via netmail messages addressed to one
; of the following robot names at one of your addresses.
; The message must have the necessary password as its subject; the text
; contains your commands.
;
RemFile FMan ; FMan is a file-robot name
;RemFile Fsearch
;RemFile Maint
;RemFile AutoMaint
;
;
; The access to areas and commands is based on the Maximus 3.xx "Access
; String" concept.
; Each "RFAccess <pwd> <acs> [<points>]" statement grants the
; specified <acs> to the specified <pwd>.
;
; ATTENTION: The robot's answers are sent to the listed <points> ONLY.
; The answer to passworded messages are NOT sent to the sender but only
; to the listed points. Of course the legitimate user of the password must
; be listed in <points> !
;
RFAccess password1 SysOp/M1 1 2 4
RFAccess password2 AsstSysOp/M1 1 2 4
RFAccess password3 AsstSysOp/1 1 2 5
RFAccess password4 Clerk/1 1 2 20
;
; Some commands could be useful for general points or remote users too:
; "RFDefAccess <acs> [<points>]" grants <acs> to users that do not put any
; recognized password in the subject.
; The robot's answers are sent to the listed <points> _AND_ to the
; request originating address.
;
RFDefAccess Normal 0 1
;
; Some misused commands could determine an enourmous output
; (e.g. dir *.*): let's put an upper limit on the number of response
; messages (the msg size is already limited by the MsgSize statement):
;
RFMaxMsgs 5
;
;
HelpPath fman.hlp ; Full path to the help file.
; ; Needed for the help command.
; ; You can specify the filename alone if it is
; ; in the current directory.
;
DefDays 30 ; Files newer than <DefDays> days are
; ; marked with an '*'. The NewFiles command
; ; defaults to <DefDays> days.
;
;
UseFB ; Use FileBase if available.
; ; Use *.IDX, *.DAT, *.DMP if available
; ; whenever useful.
; ; Filebase files will be automatically updated
; ; when executing filemanager commands.
; ; (no necessity for external FB/FBP.EXE).
;
; UniqueDmpLine ; When multi-line descriptions are
; ; used, the generated FILES.DMP
; ; will contain a unique line
; ; (resulting from the concatenation
; ; of all description lines).
;
;
; And now the commands !
;
; Each command is regulated by a statement:
;
; <command> <acs> [<areas>]
;
; where:
;
; <command> is the name of a FileManager command
; <acs> is the Maximus access string required to use <command>
; <areas> is a list of areas that can contain wildcards ("OS/2 style")
; and defaults to "*" (all areas).
;
; When a command is issued, the FileManager checks the list of
; statements that define the access rights from the bottom up (last to
; first). The first match between the current area name and <areas>
; determines the <acs> requirements for executing the requested command
; in the current area.
;
; E.g.
;
; Kill SysOp|AsstSysOp/U
; Kill SysOp private.*
;
; Specifies that the Kill command requires SysOp or AsstSysOp/U
; privilege in all areas but private.*, which are reserved to SysOp
; only.
;
;
; KillTo SysOp
; KillTo AsstSysOp/U msdos.* win.*
;
; Specifies that the KillTo command requires AsstSysOp/U privilege in
; msdos.* and win.* areas, SysOp in all the others.
;
;
;
; Usually you should use a "<command> <acs>" statement first, to
; specify default access requirements, then you can add other
; "<command> <acs> <areas>" statements to override the default
; requirements for the specified areas.
;
; See FMAN.HLP (or send a message to the robot with the HELP command)
; for a description of the available commands.
;
;
;
Help Twit ; help on available commands.
; ; The help text on available commands ONLY
; ; will be put in the response message
; ; (e.g. Twits will not be informed about
; ; SysOp level commands).
; ; _NO_ area-override available.
;
Areas Twit ; List of available areas.
; ; _NO_ area-override available.
;
Dir Twit ; search for filespec.
; ; filespec follows the OS format when using
; ; FILES.BBS and the OS/2 one when FB is used.
; ; e.g. DIR NODE *diff.* is acceptable with FB
; ; even under Dos.
;
Cont Twit ; list contents
;
Locate Twit ; search file name and description for
; ; the specified token
;
Type Twit ; type text file
Type Normal/EF NET.TEXT.* ; The Type command in NET.TEXT.* areas
; ; is restricted to people who use a
; ; password that grants Normal/EF access.
;
Files Twit ; list of files in one area
;
NewFiles Twit ; list of new files
;
;
;
; SysOpCommands <acs> [<areas>]
;
; It defines access requirements for all the following commands:
;
; Hurl, Kill, KillTo, Edit, Ren, Touch, DelAft, AddAft, SortAft.
;
; After "SysOpCommands" you can use the single statements as overrides.
;
; E.g.:
;
; SysOpCommands AsstSysOp
; SysOpCommands AsstSysOp/u local.1!*
; KillTo AsstSysOp/u
;
; Specifies that the "SysOp" commands require a password that grants
; AsstSysOp privilege. The "local.1!*" areas and the "KillTo" command
; require the 'u' key also.
;
SysOpCommands AsstSysOp/M
SysOpCommands AsstSysOp ATARI.* AMIGA.*
SysOpCommands Clerk MAC.*
;
; Hurl Clerk MAC.* ; these 9 statements are equivalent to
; Kill Clerk MAC.* ; the previous SysOpCommands one.
; KillTo Clerk MAC.*
; Edit Clerk MAC.*
; Ren Clerk MAC.*
; Touch Clerk MAC.*
; DelAft Clerk MAC.*
; AddAft Clerk MAC.*
; SortAft Clerk MAC.*
;
;
; A R E A F I X
;
; (Squish)
;
;
; You must send areafix requests to one of the following names; to disable
; Areafix you can comment out all the "Areafix <name>" lines.
;
AreaFix AreaFix ; Areafix Akas
AreaFix AutoEcho
;
AFDescFile c:\max\misc\echo.lst ; The echo description file, copied to
; ; a message in answer to a -L request.
; ; Please do not insert TAB characters
; ; in this file: use spaces only !
;
AFHelpFile c:\nmfwd\AFHelp.txt ; A Areafix help file to be sent in
; ; response to -h or %Help commands.
; ; Please do not insert TAB characters
; ; in this file: use spaces only !
;
AFanswer 1 2 ; Areafix answers are forwarded to these points.
;
;
; RESCAN
;
; BeforeRescan <cmd>
; RescanCmd <cmd>
; AfterRescan <cmd>
;
; These three statements define the actions to be taken for
; rescanning an echomail area (in response to a -R in the subject).
; In the case you have different routing schedules for echomail and
; netmail, you will need something similar to the example, otherwise
; you can usually comment out BeforeRescan and AfterRescan.
;
; BeforeRescan and AfterRescan are executed one time only, before the first
; rescan and after the last one.
;
; <cmd> can be any executable or batch file with the necessary command
; line parameters. %t and %n are converted to the area tag and node
; address respectively.
;
; IMPORTANT: please note that if you specify a path for Squish you must
; also specify the config file: e.g.
; "c:\squish\squish -cc:\squish\squish.cfg -l rescan %t %n"
; Anyway you might prefer changing directory using BeforeRescan and
; AfterRescan.
;
BeforeRescan squish squash -o -sNET ; Packs netmail in temporary outbound
;
RescanCmd squish -l rescan %t %n ; Rescans area %t to node %n
;
AfterRescan squish squash -o -sECHO ; Packs rescanned echomail
;
;
; ACCESS CONTROL
;
; AFAccess <address> <password> <N|H|D|C> <level> [<keys>]
; <address> is a 4D address;
; <password> is not case sensitive and has no length limit;
; <level> is an integer in the range 0..65535
; <keys> is a set of keys chosen from 1..8,A..X (as in Maximus 2.0).
; The AFAccess statement gives the <level> and <keys> access rights to
; <address> with <password>. You can control the flavour of the answer
; packet with the <N|H|D|C> field: N for Normal (you should use this
; unless you have some special necessity), H for Hold, D for Direct
; (the Crash and Hold flags are raised in the message, due to Squish's
; handling of message flags), C for Crash.
; 3D Points MUST be listed with the fakenet address.
;
AFAccess 2:22504/1 password1 N 100 AP
AFAccess 2:22504/2 password2 N 50 P
AFAccess 2:332/504.3 password3 N 10 P
AFAccess 2:332/501 password4 H 20
;
; AFDefProt <level> [<keys>]
; The AfDefProt statement gives a default access level to areas not
; listed in AFProt statements.
;
AFDefProt 10
;
; AFProt <echotag> <level> [<keys>]
; The AFProt statement gives the <level> and <keys> access level
; protection to area <echotag>: an authorized system must have in its
; AFAccess definition a privilege level not less than <level> and at
; least all the <keys>.
;
AFProt LOCALE_332.504 100 P
;